Priorities

Many statements in this manual use <priority> as a component. A priority determines the order in which competing commands are fulfilled. For example, priority determines which of two competing requests to USE a resource gets fulfilled, or which of two competing requests to SEND the same entities to different locations gets fulfilled. Commands or entities with high enough priority can even bring back up locations that are down, or force a location to stop processing one entity and process another instead. This is called "preemption." All priorities must be an expression that evaluates to a number between 0 and 999.

For a complete explanation of priorities and preemption, see Location Priorities and Preemption, Resource Shift Downtime Priorities, Preemptive Entities, and Preemption Process Logic.